Login Request

Function

The login establishes a session with RRI. The login is transmitted to RRI in form of a request.

Features

If there are 10 consecutive incorrect logins, the user will be blocked for one hour and all further login attempts will be rejected. As long as the blocking is active, no logins are permitted, even if the data is valid.

  • Login requests are not part of the quotas.
  • The password should:
    • have at least 12 characters,
    • have a sufficiently secure entropy (> 70 bit),
    • be changed immediately in the event of loss or compromise,
    • always be created anew and must not correspond to a previously used password.

Request Parameters

An request consists of the keywords or elements listed below:

K/V Keyword XML Namespace and Element

Occurrence
min - max

 Type / Length Value Range Description
Action login 1 enumeration login-erule request type
Version - 1 enumeration version-erule This is the version. The keyword is only relevant for requests in the key/value format.
User user 1 token 9 – 32 contact-rule An RRI login must be used as value for the user. The RRI login is stored in the RegAcc profile in the "RRI Login" line.

The RegAcc profile is maintained via the RAI (see documentation "RAI - Registrar Administration Interface", How to Edit the RegAcc Profile).
Password password 1 token 1 - 255 Any visible Unicode character (according to Unicode version 3.1 This is the user password in clear text, no value range is defined.

 

Examples

  • xml
  • k/v

Copy

format: xml
request: logout

<!-- request -->

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<registry-request xmlns="http://registry.denic.de/global/5.0">
 <logout/>
</registry-request>

 

Copy

format: xml
response: logout

<?xml version="1.0" encoding="UTF-8"?>

<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
  <tr:transaction>
    <tr:stid>078db1bf-9f0a-11df-a9e2-9519b5688882</tr:stid>
    <tr:result>success</tr:result>
  </tr:transaction>
</registry-response>

Copy

format: k/v
request: logout

Version: 5.0
Action: logout

 

Copy

format: k/v
response: logout

Result: success
STID: 0b97f9b7-9f0b-11df-a9e2-9519b5688882